Access Logs for 193.174.89.19

April 27, 2025, 10:45 p.m. — GET /r4/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 10:45 p.m. — GET /r3/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 10:45 p.m. — GET /r5/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 10:45 p.m. — GET /fhir/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /r2/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /r4/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseR5/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /fhir/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /r5/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseDstu3/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /fhir-server/api/v4/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseR4/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseR3/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /r3/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseDstu2/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /fhir-server/api/v4/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 27, 2025, 8:31 p.m. — GET /baseR2/metadata → 400
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseR5/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseDstu3/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /r3/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /r2/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseR2/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseDstu2/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseR3/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /baseR4/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /fhir-server/api/v4/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /r5/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de
April 26, 2025, 1:56 a.m. — GET /fhir/metadata → 404
User-Agent: FH Muenster/Security-Scanner/fh-muenster.de