Domain > www2.philembassy.net

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2025-01-20	220.247.10.248 (ClassC)

HTTP/1.1 200 OKServer: nginxDate: Mon, 20 Jan 2025 11:16:41 GMTContent-Type: text/htmlContent-Length: 10701Last-Modified: Mon, 01 Jun 2020 03:54:02 GMTConnection: keep-aliveVary: Accept-EncodingETag: 5ed47bda-29cdAccept-Ranges: bytes

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd>html xmlnshttp://www.w3.org/1999/xhtml>  head>    meta http-equivContent-Type contenttext/html; charsetUTF-8 />    title>Apache2 Debian Default Page: It works/title>    style typetext/css mediascreen>  * {    margin: 0px 0px 0px 0px;    padding: 0px 0px 0px 0px;  }  body, html {    padding: 3px 3px 3px 3px;    background-color: #D8DBE2;    font-family: Verdana, sans-serif;    font-size: 11pt;    text-align: center;  }  div.main_page {    position: relative;    display: table;    width: 800px;    margin-bottom: 3px;    margin-left: auto;    margin-right: auto;    padding: 0px 0px 0px 0px;    border-width: 2px;    border-color: #212738;    border-style: solid;    background-color: #FFFFFF;    text-align: center;  }  div.page_header {    height: 99px;    width: 100%;    background-color: #F5F6F7;  }  div.page_header span {    margin: 15px 0px 0px 50px;    font-size: 180%;    font-weight: bold;  }  div.page_header img {    margin: 3px 0px 0px 40px;    border: 0px 0px 0px;  }  div.table_of_contents {    clear: left;    min-width: 200px;    margin: 3px 3px 3px 3px;    background-color: #FFFFFF;    text-align: left;  }  div.table_of_contents_item {    clear: left;    width: 100%;    margin: 4px 0px 0px 0px;    background-color: #FFFFFF;    color: #000000;    text-align: left;  }  div.table_of_contents_item a {    margin: 6px 0px 0px 6px;  }  div.content_section {    margin: 3px 3px 3px 3px;    background-color: #FFFFFF;    text-align: left;  }  div.content_section_text {    padding: 4px 8px 4px 8px;    color: #000000;    font-size: 100%;  }  div.content_section_text pre {    margin: 8px 0px 8px 0px;    padding: 8px 8px 8px 8px;    border-width: 1px;    border-style: dotted;    border-color: #000000;    background-color: #F5F6F7;    font-style: italic;  }  div.content_section_text p {    margin-bottom: 6px;  }  div.content_section_text ul, div.content_section_text li {    padding: 4px 8px 4px 16px;  }  div.section_header {    padding: 3px 6px 3px 6px;    background-color: #8E9CB2;    color: #FFFFFF;    font-weight: bold;    font-size: 112%;    text-align: center;  }  div.section_header_red {    background-color: #CD214F;  }  div.section_header_grey {    background-color: #9F9386;  }  .floating_element {    position: relative;    float: left;  }  div.table_of_contents_item a,  div.content_section_text a {    text-decoration: none;    font-weight: bold;  }  div.table_of_contents_item a:link,  div.table_of_contents_item a:visited,  div.table_of_contents_item a:active {    color: #000000;  }  div.table_of_contents_item a:hover {    background-color: #000000;    color: #FFFFFF;  }  div.content_section_text a:link,  div.content_section_text a:visited,   div.content_section_text a:active {    background-color: #DCDFE6;    color: #000000;  }  div.content_section_text a:hover {    background-color: #000000;    color: #DCDFE6;  }  div.validator {  }    /style>  /head>  body>    div classmain_page>      div classpage_header floating_element>        img src/icons/openlogo-75.png altDebian Logo classfloating_element/>        span classfloating_element>          Apache2 Debian Default Page        /span>      /div>!--      div classtable_of_contents floating_element>        div classsection_header section_header_grey>          TABLE OF CONTENTS        /div>        div classtable_of_contents_item floating_element>          a href#about>About/a>        /div>        div classtable_of_contents_item floating_element>          a href#changes>Changes/a>        /div>        div classtable_of_contents_item floating_element>          a href#scope>Scope/a>        /div>        div classtable_of_contents_item floating_element>          a href#files>Config files/a>        /div>      /div>-->      div classcontent_section floating_element>        div classsection_header section_header_red>          div idabout>/div>          It works!        /div>        div classcontent_section_text>          p>                This is the default welcome page used to test the correct                 operation of the Apache2 server after installation on Debian systems.                If you can read this page, it means that the Apache HTTP server installed at                this site is working properly. You should b>replace this file/b> (located at                tt>/var/www/html/index.html/tt>) before continuing to operate your HTTP server.          /p>          p>                If you are a normal user of this web site and dont know what this page is                about, this probably means that the site is currently unavailable due to                maintenance.                If the problem persists, please contact the sites administrator.          /p>        /div>        div classsection_header>          div idchanges>/div>                Configuration Overview        /div>        div classcontent_section_text>          p>                Debians Apache2 default configuration is different from the                upstream default configuration, and split into several files optimized for                interaction with Debian tools. The configuration system is                b>fully documented in                /usr/share/doc/apache2/README.Debian.gz/b>. Refer to this for the full                documentation. Documentation for the web server itself can be                found by accessing the a href/manual>manual/a> if the tt>apache2-doc/tt>                package was installed on this server.          /p>          p>                The configuration layout for an Apache2 web server installation on Debian systems is as follows:          /p>          pre>/etc/apache2/|-- apache2.conf|       `--  ports.conf|-- mods-enabled|       |-- *.load|       `-- *.conf|-- conf-enabled|       `-- *.conf|-- sites-enabled|       `-- *.conf          /pre>          ul>                        li>                           tt>apache2.conf/tt> is the main configuration                           file. It puts the pieces together by including all remaining configuration                           files when starting up the web server.                        /li>                        li>                           tt>ports.conf/tt> is always included from the                           main configuration file. It is used to determine the listening ports for                           incoming connections, and this file can be customized anytime.                        /li>                        li>                           Configuration files in the tt>mods-enabled//tt>,                           tt>conf-enabled//tt> and tt>sites-enabled//tt> directories contain                           particular configuration snippets which manage modules, global configuration                           fragments, or virtual host configurations, respectively.                        /li>                        li>                           They are activated by symlinking available                           configuration files from their respective                           *-available/ counterparts. These should be managed                           by using our helpers                           tt>                                a2enmod,                                a2dismod,                           /tt>                           tt>                                a2ensite,                                a2dissite,                            /tt>                                and                           tt>                                a2enconf,                                a2disconf                           /tt>. See their respective man pages for detailed information.                        /li>                        li>                           The binary is called apache2. Due to the use of                           environment variables, in the default configuration, apache2 needs to be                           started/stopped with tt>/etc/init.d/apache2/tt> or tt>apache2ctl/tt>.                           b>Calling tt>/usr/bin/apache2/tt> directly will not work/b> with the                           default configuration.                        /li>          /ul>        /div>        div classsection_header>            div iddocroot>/div>                Document Roots        /div>        div classcontent_section_text>            p>                By default, Debian does not allow access through the web browser to                em>any/em> file apart of those located in tt>/var/www/tt>,                a hrefhttp://httpd.apache.org/docs/2.4/mod/mod_userdir.html relnofollow>public_html/a>                directories (when enabled) and tt>/usr/share/tt> (for web                applications). If your site is using a web document root                located elsewhere (such as in tt>/srv/tt>) you may need to whitelist your                document root directory in tt>/etc/apache2/apache2.conf/tt>.            /p>            p>                The default Debian document root is tt>/var/www/html/tt>. You                can make your own virtual hosts under /var/www. This is different                to previous releases which provides better security out of the box.            /p>        /div>        div classsection_header>          div idbugs>/div>                Reporting Problems        /div>        div classcontent_section_text>          p>                Please use the tt>reportbug/tt> tool to report bugs in the                Apache2 package with Debian. However, check a                hrefhttp://bugs.debian.org/cgi-bin/pkgreport.cgi?orderingnormal;archive0;srcapache2;repeatmerged0                relnofollow>existing bug reports/a> before reporting a new bug.          /p>          p>                Please report bugs specific to modules (such as PHP and others)                to respective packages, not to the web server itself.          /p>        /div>      /div>    /div>    div classvalidator>    /div>  /body>/html>

Subdomains

Date	Domain	IP
mail10.philembassy.net	2024-11-04	220.247.10.248
mail01.philembassy.net	2025-01-20	220.247.10.248
smtp01.philembassy.net	2024-12-25	220.247.10.248
mail1.philembassy.net	2024-12-28	220.247.10.248
imap1.philembassy.net	2024-12-06	220.247.10.248
smtp1.philembassy.net	2025-01-10	220.247.10.248
server1.philembassy.net	2025-01-03	220.247.10.248
ms1.philembassy.net	2024-11-04	220.247.10.248
www1.philembassy.net	2025-01-01	220.247.10.248
mx1.philembassy.net	2024-12-02	220.247.10.248
mail02.philembassy.net	2025-01-20	220.247.10.248
mx02.philembassy.net	2024-11-04	220.247.10.248
mail2.philembassy.net	2025-01-18	220.247.10.248
smtp2.philembassy.net	2024-12-31	220.247.10.248
server2.philembassy.net	2024-09-17	220.247.10.248
ns2.philembassy.net	2024-11-04	220.247.10.248
www2.philembassy.net	2025-01-20	220.247.10.248
mx2.philembassy.net	2024-12-18	220.247.10.248
relay2.philembassy.net	2024-12-31	220.247.10.248
mail3.philembassy.net	2025-01-20	220.247.10.248
pop3.philembassy.net	2025-01-18	220.247.10.248
smtp3.philembassy.net	2024-12-05	220.247.10.248
mx3.philembassy.net	2025-01-20	220.247.10.248
mail4.philembassy.net	2025-01-18	220.247.10.248
mail5.philembassy.net	2025-01-20	220.247.10.248
mail6.philembassy.net	2024-11-04	220.247.10.248
mail7.philembassy.net	2024-12-26	220.247.10.248
mail9.philembassy.net	2024-12-09	220.247.10.248
barracuda.philembassy.net	2024-12-09	220.247.10.248
www.osaka.philembassy.net	2024-11-04	220.247.10.248
zimbra.philembassy.net	2024-11-29	220.247.10.248
mta.philembassy.net	2025-01-20	220.247.10.248
posta.philembassy.net	2024-12-08	220.247.10.248
poczta.philembassy.net	2024-11-04	220.247.10.248
pbrand.philembassy.net	2024-12-15	220.247.10.248
send.philembassy.net	2024-12-21	220.247.10.248
koube.philembassy.net	2025-01-20	220.247.10.248
exchange.philembassy.net	2024-12-15	220.247.10.248
home.philembassy.net	2024-12-29	220.247.10.248
comune.philembassy.net	2024-09-17	220.247.10.248
mail.comune.philembassy.net	2024-12-02	220.247.10.248
smtp.comune.philembassy.net	2025-01-09	220.247.10.248
ipe.philembassy.net	2024-11-04	220.247.10.248
secure.philembassy.net	2024-12-12	220.247.10.248
gate.philembassy.net	2025-01-20	220.247.10.248
mailgate.philembassy.net	2024-09-17	220.247.10.248
remote.philembassy.net	2024-12-16	220.247.10.248
auth.philembassy.net	2024-11-04	220.247.10.248
smtpauth.philembassy.net	2024-12-06	220.247.10.248
bangkok.philembassy.net	2024-12-21	220.247.10.248
mail.philembassy.net	2024-11-04	220.247.10.248
webmail.philembassy.net	2024-12-28	220.247.10.248
email.philembassy.net	2024-11-04	220.247.10.248
smtpmail.philembassy.net	2024-12-13	220.247.10.248
vmail.philembassy.net	2025-01-20	220.247.10.248
newmail.philembassy.net	2024-12-12	220.247.10.248
eml.philembassy.net	2024-11-04	220.247.10.248
m.philembassy.net	2024-12-13	220.247.10.248
antispam.philembassy.net	2024-11-04	220.247.10.248
sysadmin.philembassy.net	2024-11-04	220.247.10.248
correo.philembassy.net	2025-01-06	220.247.10.248
www.info.philembassy.net	2025-01-20	220.247.10.248
po.philembassy.net	2024-09-17	220.247.10.248
tokyo.philembassy.net	2024-11-04	220.247.10.248
http.tokyo.philembassy.net	2025-01-20	220.247.10.248
www.http.www.tokyo.philembassy.net	2024-12-09	220.247.10.248
toktyo.philembassy.net	2024-12-29	220.247.10.248
imap.philembassy.net	2024-12-19	220.247.10.248
pop.philembassy.net	2025-01-14	220.247.10.248
ftp.philembassy.net	2024-12-10	220.247.10.248
smtp.philembassy.net	2025-01-07	220.247.10.248
authsmtp.philembassy.net	2025-01-04	220.247.10.248
tiger.philembassy.net	2025-01-20	220.247.10.248
postmaster.philembassy.net	2024-09-17	220.247.10.248
server.philembassy.net	2024-12-18	220.247.10.248
mailserver.philembassy.net	2024-11-04	220.247.10.248
hermes.philembassy.net	2025-01-20	220.247.10.248
mails.philembassy.net	2025-01-20	220.247.10.248
ms.philembassy.net	2024-12-08	220.247.10.248
ns.philembassy.net	2024-12-14	220.247.10.248
dns.philembassy.net	2024-12-19	220.247.10.248
smtps.philembassy.net	2024-09-17	220.247.10.248
xps.philembassy.net	2025-01-05	220.247.10.248
mxs.philembassy.net	2024-12-30	220.247.10.248
direct.philembassy.net	2025-01-20	220.247.10.248
net.philembassy.net	2024-12-11	220.247.10.248
internet.philembassy.net	2025-01-08	220.247.10.248
vnet.philembassy.net	2025-01-14	220.247.10.248
root.philembassy.net	2024-09-17	220.247.10.248
art.philembassy.net	2024-12-13	220.247.10.248
host.philembassy.net	2024-12-01	220.247.10.248
mailhost.philembassy.net	2024-12-01	220.247.10.248
out.philembassy.net	2025-01-17	220.247.10.248
mailout.philembassy.net	2024-11-04	220.247.10.248
gw.philembassy.net	2024-12-06	220.247.10.248
mailgw.philembassy.net	2024-12-12	220.247.10.248
tw.philembassy.net	2024-11-04	220.247.10.248
www.philembassy.net	2024-09-17	220.247.10.248
mailx.philembassy.net	2024-12-25	220.247.10.248
mx.philembassy.net	2024-11-04	220.247.10.248
a.mx.philembassy.net	2024-12-11	220.247.10.248
box.philembassy.net	2025-01-20	220.247.10.248
mbox.philembassy.net	2025-01-10	220.247.10.248
relay.philembassy.net	2025-01-20	220.247.10.248
mailrelay.philembassy.net	2024-12-12	220.247.10.248
gateway.philembassy.net	2025-01-01	220.247.10.248

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > www2.philembassy.net

Is this malicious?

DNS Resolutions

Port 80

Subdomains