ipa02.ams02.cldin.eu. SSHFP records

SSHFP
1h
4 2 779180DC56E0716D810EB0A45D152AE0B8BEF6542C2755E2E540AB275CAFEC49
4 1 5A60D34B725BD58415EA002C3FFD07CD077E5E94
1 1 2226AC7425F3FC6BB3EBDD21826BB2370184606A
3 2 E98D7D79600CF95BB238D43FE7046DAE0315876EE8BC0688C68A8CF547836CA0
3 1 79528FC600895FBBB2D9F12F4E0760B669A05306
1 2 0DF1A5CE69B7F06A9F0B9A20703E971FB9CEE23B444E00B97BB6CD1059A33F5F

Question and response

Question

dig ipa02.ams02.cldin.eu. SSHFP

Answer

ipa02.ams02.cldin.eu. 3600 SSHFP 4 2 779180DC56E0716D810EB0A45D152AE0B8BEF6542C2755E2E540AB275CAFEC49 ipa02.ams02.cldin.eu. 3600 SSHFP 4 1 5A60D34B725BD58415EA002C3FFD07CD077E5E94 ipa02.ams02.cldin.eu. 3600 SSHFP 1 1 2226AC7425F3FC6BB3EBDD21826BB2370184606A ipa02.ams02.cldin.eu. 3600 SSHFP 3 2 E98D7D79600CF95BB238D43FE7046DAE0315876EE8BC0688C68A8CF547836CA0 ipa02.ams02.cldin.eu. 3600 SSHFP 3 1 79528FC600895FBBB2D9F12F4E0760B669A05306 ipa02.ams02.cldin.eu. 3600 SSHFP 1 2 0DF1A5CE69B7F06A9F0B9A20703E971FB9CEE23B444E00B97BB6CD1059A33F5F

Authority

cldin.eu. 3600 NS ipa01.haa01.cldin.eu. cldin.eu. 3600 NS ipa01.ams02.cldin.eu. cldin.eu. 3600 NS ipa02.ams02.cldin.eu.

Additional

ipa01.ams02.cldin.eu. 3600 A 185.109.220.7 ipa02.ams02.cldin.eu. 3600 A 185.107.214.229 ipa01.haa01.cldin.eu. 3600 A 31.25.97.69 ipa01.ams02.cldin.eu. 3600 AAAA 2a0b:8f80:1:0:5054:ff:fe8f:2466 ipa02.ams02.cldin.eu. 3600 AAAA 2a05:1500:601:3:5054:ff:fe0d:9fa7 ipa01.haa01.cldin.eu. 3600 AAAA 2a05:1500:701:206:5054:ff:fedb:6167 . 0 OPT ; payload 1232, xrcode 0, version 0, flags 0

About these results

This page shows the SSHFP records for ipa02.ams02.cldin.eu.. SSHFP records publish SSH host key fingerprints in DNS. With DNSSEC validation, clients can use them to verify server host keys and reduce man-in-the-middle risk.

Find other DNS records for ipa02.ams02.cldin.eu.:

The results on this page are freshly fetched just for you when you loaded this page. Wirewiki queried the authoritative DNS servers for ipa02.ams02.cldin.eu.. That means that these results are guaranteed to be accurate, because there are no caches in between that could potentially cause staleness.

To look up SSHFP records for another hostname or domain name, go back to SSHFP lookup, or use DNS lookup to find all DNS records.