marys

ATLANTIC RECORDS

Oct 16th, 2014
408
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.86 KB | None | 0 0
  1. http://www.atlanticrecords.com/ INTEL REPORT BY *HACKTIVIST_15 . ANONYMOUS FAMILIA <3 <3 <3 <3 <3 <3
  2.  
  3. IP Address 23.0.160.19 < deploy.static.akamaitechnologies.com >
  4.  
  5. Starting Nmap 6.01 ( http://nmap.org ) at 2014-10-16 04:37 EDT
  6. Nmap scan report for a23-0-160-19.deploy.static.akamaitechnologies.com (23.0.160.19)
  7. Host is up (0.0089s latency).
  8. Not shown: 998 filtered ports
  9. PORT STATE SERVICE VERSION
  10. 80/tcp open http AkamaiGHost (Akamai's HTTP Acceleration/Mirror service)
  11. 443/tcp open ssl/http AkamaiGHost (Akamai's HTTP Acceleration/Mirror service)
  12.  
  13.  
  14. HTTP Server Header: nginx
  15.  
  16. Server Type nginx
  17.  
  18. DNS resolves 'www.atlanticrecords.com' to 64.78.224.186
  19.  
  20. DNS resolves 'www.atlanticrecords.com' to 64.78.224.184
  21.  
  22. TLS 1.2, TLS 1.1, TLS 1.0, SSL 3.0
  23.  
  24. SSL 3.0 is an outdated protocol version with known vulnerabilities
  25.  
  26. -----------------------------------------------------------------------------------------------------
  27. -----------------------------------------------------------------------------------------------------
  28.  
  29. server domain
  30.  
  31. 1. 162.249.107.229 www.atlanticrecords.com assets.atlanticrecords.co.uk
  32.  
  33. SSL Configuration
  34.  
  35. .SSL 3.0 Disabled:Fail
  36. .Certificates configured correctly:Fail
  37. .BEAST Vulnerability:Fail
  38. .OCSP Stapling:Fail
  39. .FIPS Compliant:Fail
  40.  
  41. HTTP Tests:
  42.  
  43. .Strict Transport Security:Fail
  44. .Mixed Content (HTTP and HTTPS):Timed Out
  45. .Domain name resolves to IPv6 address:Fail
  46.  
  47. Server Details Icon
  48. Server:Apache
  49. IP Address:162.249.107.229
  50. Port:443
  51. Hostname:www.atlanticrecords.com
  52.  
  53.  
  54. EXPLOITS: Sessions may be vulnerable to BEAST attack
  55. Attackers may be able to decrypt the encrypted SSL traffic
  56.  
  57. Hostname in certificate and DNS name do not match
  58. Users will receive strong browser warnings
  59.  
  60. Server has not enabled HTTP Strict-Transport-Security
  61. Users may be exposed to man-in-the-middle attacks
  62.  
  63. =====================================================================================================
  64.  
  65.  
  66. 2. 184.28.16.67 www.atlanticrecords.com a248.e.akamai.net
  67. *.akamaihd.net
  68. *.akamaihd-staging.net
  69. *.akamaized.net
  70. *.akamaized-staging.net
  71. Server:nginx
  72. IP Address:184.28.16.67
  73. Port:443
  74. Hostname:www.atlanticrecords.com
  75.  
  76.  
  77. EXPLOITS:Server does not use secure renegotiation settings
  78. Site is more vulnerable to Denial of Service (DOS) attacks
  79.  
  80. Hostname in certificate and DNS name do not match
  81. Users will receive strong browser warnings
  82.  
  83. Server has not enabled HTTP Strict-Transport-Security
  84. Users may be exposed to man-in-the-middle attacks
  85.  
  86. Server uses RC4 cipher with modern browsers
  87. More secure ciphers are available for TLS 1.1 and newer
  88.  
  89. Server is using RC4-based ciphersuites which have known vulnerabilities
  90. Evaluate your client compatibility requirements to determine if you can disable RC4-based ciphersuites
  91.  
  92. ======================================================================================================
  93.  
  94. 3. 184.28.16.106 www.atlanticrecords.com a248.e.akamai.net
  95. *.akamaihd.net
  96. *.akamaihd-staging.net
  97. *.akamaized.net
  98. *.akamaized-staging.net
  99.  
  100. EXPLOITS:
  101. Server does not use secure renegotiation settings
  102. Site is more vulnerable to Denial of Service (DOS) attacks
  103.  
  104. Hostname in certificate and DNS name do not match
  105. Users will receive strong browser warnings
  106.  
  107. Server uses RC4 cipher with modern browsers
  108. More secure ciphers are available for TLS 1.1 and newer
  109.  
  110. Server has not enabled HTTP Strict-Transport-Security
  111. Users may be exposed to man-in-the-middle attacks
  112.  
  113. Site is using certificate from CA that doesn’t support IPv4
  114. IPv4-only users may experience errors when visiting your site.
  115.  
  116. Server doesn’t prefer ciphers that enable forward secrecy.
  117. Encrypted communications captured today are at risk of being decrypted by an attacker in the future.
  118.  
  119. Server is using RC4-based ciphersuites which have known vulnerabilities
  120. Evaluate your client compatibility requirements to determine if you can disable RC4-based ciphersuites
  121.  
  122. Server has SSL v3 enabled
  123. SSL v3 should be disabled if compatibility with older mobile clients is not required
  124.  
  125.  
  126. =====================================================================================================
Advertisement
Add Comment
Please, Sign In to add comment